Setting harq timing for pdsch with pending pdsch-to-harq-timing-indicator

ABSTRACT

Methods and systems for setting Hybrid Automatic Repeat Request (HARQ) timing for Physical Downlink Shared Channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator (PHTI) are provided. In one aspect, a method performed by a wireless device comprises: receiving a first Downlink Control Information (DCI) associated with a first Downlink (DL) data transmission, the first DCI comprising a non-numerical PHTI; receiving the first DL data transmission; determining a HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI comprising a numerical PHTI indicating a location for HARQ feedback associated with the second DL data transmission; setting the location of HARQ feedback associated with the first DL data transmission to be the same as the location of HARQ feedback associated with the second DL data transmission; and transmitting the HARQ feedback associated with the first DL data transmission at the set location.

RELATED APPLICATIONS

This application claims the benefit of provisional patent applicationSer. No. 62/836,228, filed Apr. 19, 2019, the disclosure of which ishereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

This application relates to Physical Downlink Shared Channel (PDSCH) toHybrid Automatic Repeat Request (HARQ) timing and in particular tosetting HARQ timing for PDSCH by means of a pendingPDSCH-to-HARQ-timing-indicator.

BACKGROUND

New Radio (NR) provides the flexibility in Hybrid Automatic RepeatRequest (HARQ) feedback timing to account for dynamic Time DivisionDuplexing (TDD) and also possibly combine several HARQ feedbacks forboth lower overhead and higher reliability.

FIG. 1 illustrates Hybrid Automatic Repeat Request (HARQ) feedbackaccording to a conventional NR system. The timing (referred to as K1)between a Downlink (DL) data transmission (e.g., 100A, 100B, and so on)on a Physical Downlink Shared Channel (PDSCH) and its corresponding HARQAcknowledgement (ACK) or Negative Acknowledgement (NACK) (e.g., 102A,102B, and so on) on a Physical Uplink Control Channel (PUCCH) isdetermined based on a 3-bit field in the Downlink Control Information(DCI) within a Physical Downlink Control Channel (PDCCH) for therespective DL data transmission. Radio Resource Control (RRC) messagesconfigure the User Equipment (UE) with a set of 8 values to be indexedby the 3-bit field in the DCI to produce a value for K1 (possible valuerange is {0, 1, . . . , 15}) to be used by the UE for the timing of thecorresponding HARQ. As illustrated in FIG. 1, HARQ 102A occurs withinthe same slot (half subframe) as its corresponding DL data transmission100A, and HARQ 102B occurs in the next slot after the slot that containsits corresponding DL data transmission 100B.

NR provides the flexibility to include aggregate feedback correspondingto multiple HARQ processes in one PUCCH/Uplink Control Information (UCI)transmission by means of semi-static codebooks and/or dynamic codebooks.As illustrated in FIG. 1, the HARQ for DL data transmissions 100C and100D occur in a combined HARQ 102C.

Semi-Static HARQ Codebook

For semi-static HARQ codebooks, the codebook size in time (DLassociation set) is determined based on the configured set of HARQ-ACKtimings K1, PDCCH monitoring occasions, and semi-static configured TDDpatterns. For each slot, the UE needs to report a HARQ feedback bitmapof fixed size according to its Carrier Aggregation (CA) and TransportBlock (TB)/Code Block Group (CBG) configuration. In this example, thebitmap size is 7 bits. For TBs/CBGs not received, the corresponding bitin the HARQ feedback bitmap is set to indicate a NACK.

Dynamic HARQ Codebook

Dynamic HARQ codebooks provide the possibility to dynamically determinethe set of HARQ process for which the HARQ feedback should be reported.The DCI includes:

-   -   a Downlink Assignment Indicator (DAI), which indicates the        number of HARQ processes that should reported; and    -   a PDSCH to HARQ-ACK timing (ΔT), which specifies the time        resource in which the eNB is expecting the feedback, e.g., as a        time offset.

DAI Computation for Dynamic HARQ Codebook

The UE refers to the DAI value to calculate the dynamic HARQ codebooksize. For every PDSCH transmission, the DAI value in the DCI isincremented. The DAI in the DL scheduling DCI should be stepped by oneas compared to the immediate preceding DL scheduling DCI, if not, it isan indication that PDSCH transmission(s) has been missed. The differencebetween the two received DAI values at the UE in current and earlier DCIindicates how many PDSCH transmissions were missed.

FIG. 2 shows one example of combined HARQ feedback according to aconventional NR system. In FIG. 2, each slot contains a PDCCH with DCIvalues that include a DAI value and a ΔT value, followed by a PDSCH thatcontains a DL data transmission. In the example illustrated in FIG. 2,the values for DAI and ΔT are shown below the respective PDCCH block,arbitrarily numbered from one to seven. Moving from left to right, PDCCH1 has a DAI value of 1, indicating to the UE that a HARQ will be neededfor the PDSCH that immediately follows the first PDCCH, PDSCH 1. The ΔTvalue equals 6, indicating that the UE is expected to provide HARQfeedback 6 slots later. PDCCH 2 has a DAI value of 2, indicating to theUE that a HARQ will be needed for two PDSCHs, i.e., PDSCH 1 and PDSCH2.The ΔT value equals 5, indicating to the UE that it should provide HARQfeedback 5 slots later. PDCCH 3 has a DAI value of 3, indicating to theUE that a HARQ will be needed for each of three PDSCHs, i.e., PDSCH 1,PDSCH 2, and PDSCH 3.

This sequence continues, with the ΔT decreasing as the time for the UEto provide HARQ feedback to the NR base station (gNB) gets closer, andthe DAI increasing as the number of HARQ processes that should reportedincreases. However, the DAI value in NR release 15 (rel-15) is only twobits (representing four possible values 0, 1, 2, 3); after reaching thehighest DAI value (i.e., 3), the DAI value rolls over and starts againfrom the smallest value. This is shown in FIG. 2, where PDCCH 4 includesa DAI with a value of 0. PDSCH 7 is too close to the PDCCH to beincluded in the combined HARQ feedback, so PDCCH will include HARQfeedback for PDSCH 1 through PDSCH 6.

FIG. 3 shows another example of combined HARQ feedback according to aconventional NR system. In the example illustrated in FIG. 3, PUCCH 1includes the HARQ feedback for PDSCH 1 and PDSCH 2. PDSCH 3 is too closeto PUCCH 1, so PUCCH 2 includes the HARQ feedback for PDSCH 3, PDSCH 4,and PDSCH 5. In FIG. 3, PDSCH 6 is too close to PUCCH 2, so HARQfeedback for PDSCH 6 will need to be reported in a later PUCCH not shownin FIG. 3.

Problems with Conventional Systems

FIG. 4 illustrates one problem suffered by a conventional NR system. NRsupports small processing delays, but not as small as to allow providingHARQ feedback within the same slot as the corresponding DL datatransmission. For instance, with a Subcarrier Spacing (SPS) of 15kilohertz (kHz), the Layer 1 (L1) processing delay from the end of thePDSCH until the beginning of the PUCCH is a minimum of 8 OrthogonalFrequency Division Multiplexing (OFDM) symbols assuming a capability 1for a UE. Therefore, there will be an eight OFDM symbol gap between thePDSCH reception and the corresponding feedback via the PUCCH. For SCS of30 kHz, HARQ feedback for PDSCH in slot n cannot be included in thePUCCH in slot n, and for SCS of 60 kHz, feedback the PDSCH in both slotn and n−1 cannot be included. As a result, HARQ feedback for thosePDSCHs will have to occur in a later PUCCH.

However, that later time might fall outside the gNB's Channel OccupancyTime (COT). In that case, the UE may have to sense the channel accordingto a category 4 Listen Before Talk (LBT) before sending the feedback,which increases the chances that the UE will fail to provide thefeedback at the indicated timing.

For this reason, the Third Generation Partnership Project (3GPP) NR inthe unlicensed spectrum (NR-U) working group decided to support thepossibility to postpone the HARQ feedback in order to give the UE achance to send the feedback at a later time, possibly within another gNBinitiated COT where the UE can send the feedback with fast LBT or evenwithout LBT, depending on the situation:

Agreement:

-   -   A non-numerical value is added to the possible range of        PDSCH-to-HARQ-timing-indicator values defined in Rel-15, and is        used to indicate to the UE that the HARQ-ACK feedback for the        corresponding PDSCH is postponed until the timing and resource        for the HARQ-ACK feedback is provided by the gNB.

However, the UE behavior when receiving this indication is not clear,and the mechanism to trigger the pending feedback is not specified.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. The present disclosurespecifies UE behavior when receiving a non-numerical K1 value thatindicates that the HARQ feedback is postponed.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein. Certain embodiments may provide oneor more of the following technical advantage(s). The UE behavior whenreceiving non-numerical K1 value is undefined and the present disclosureprovides different alternatives on how to resolve the issue.

SUMMARY

Methods and systems for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator are provided.

According to one aspect of the present disclosure, a method, performedby a wireless device, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: receiving a first DownlinkControl Information (DCI) associated with a first Downlink (DL) datatransmission, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator; receiving the first DL datatransmission; determining a HARQ feedback for the first DL datatransmission; receiving a second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location in time for HARQfeedback associated with the second DL data transmission; setting alocation in time of HARQ feedback associated with the first DL datatransmission to be the same as the location in time of HARQ feedbackassociated with the second DL data transmission; and transmitting theHARQ feedback associated with the first DL data transmission at the setlocation in time.

In some embodiments, receiving the second DCI comprises receivinginformation indicating a number of how many HARQ processes should bereported, the number including all pending PDSCHs and all PDSCHs havinga DCI comprising a non-numerical PDSCH-to-HARQ-timing-indicator since alast PDSCH have a DCI comprising a numericalPDSCH-to-HARQ-timing-indicator.

In some embodiments, receiving the information indicating a number ofhow many HARQ processes should be reported comprises receiving aDownlink Assignment Indicator (DAI).

In some embodiments, setting the location in time of HARQ feedbackassociated with the first DL data transmission to be the same as thelocation in time of HARQ feedback associated with the second DL datatransmission, and transmitting the HARQ feedback associated with thefirst DL data transmission at the set location in time are performedonly upon determining that the second DL data transmission is of thesame PDSCH group as the first DL data transmission.

In some embodiments, receiving the second DCI associated with the secondDL data transmission comprises receiving a User Equipment (UE)-specificDCI transmitted on a Physical Downlink Control Channel (PDCCH) theUE-specific DCI comprising the PDSCH-to-HARQ-timing-indicator.

In some embodiments, the UE-specific DCI further comprises a HARQprocess Identifier (ID).

In some embodiments, the UE-specific DCI further comprises a New DataIndicator (NDI) value corresponding to the HARQ process ID.

In some embodiments, the UE-specific DCI further comprises a PDSCH groupID and a corresponding Downlink Assignment Indicator (DAI).

In some embodiments, the UE-specific DCI further comprises a trigger bitindicating that the PDSCH-to-HARQ-timing-indicator is applicable to allPDSCHs with a pending or non-numerical PDSCH-to-HARQ-timing-indicator.

In some embodiments, the trigger bit comprises part of a DCI that isscheduling a PDSCH.

In some embodiments, the trigger bit comprises part of a DCI that is notscheduling a PDSCH.

According to one aspect of the present disclosure, a method, performedby a wireless device, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: receiving a first DownlinkControl Information (DCI) associated with a first Downlink (DL) datatransmission of a first PDSCH group, the first DCI comprising anumerical PDSCH-to-HARQ-timing-indicator; determining that a location intime for HARQ feedback that is associated with the first DL datatransmission, indicated by the numerical PDSCH-to-HARQ-timing-indicator,is too close to the first DL data transmission; and in response to thatdetermination, not transmitting the HARQ feedback that is associatedwith the first DL data transmission at the indicated HARQ transmissiontime.

In some embodiments, the method further comprises providing anindication, on the Physical Uplink Control Channel (PUCCH) at theindicated HARQ transmission time, which informs the New Radio basestation, gNB, that the HARQ feedback was postponed.

In some embodiments, the method further comprises receiving a second DCIassociated with a second DL data transmission, the second DCI comprisinga numerical PDSCH-to-HARQ-timing-indicator indicating a location in timefor HARQ feedback associated with the second DL data transmission;setting the location in time of HARQ feedback associated with the firstDL data transmission to be the same as the location in time of HARQfeedback associated with the second DL data transmission; andtransmitting the HARQ feedback associated with the first DL datatransmission at the set location in time.

According to one aspect of the present disclosure, a method, performedby a wireless device, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: receiving a first DownlinkControl Information (DCI) associated with a first Downlink (DL) datatransmission of a first PDSCH group, the first DCI comprising anumerical PDSCH-to-HARQ-timing-indicator; determining that the numericalPDSCH-to-HARQ-timing-indicator is a predefined value indicating that thecorresponding HARQ transmission on a Physical Uplink Control Channel(PUCCH) should be postponed due to a later request for another HARQtransmission on a PUCCH corresponding to another PDSCH.

In some embodiments, the method further comprises receiving a second DCIassociated with a second DL data transmission, the second DCI comprisinga numerical PDSCH-to-HARQ-timing-indicator indicating a location in timefor HARQ feedback associated with the second DL data transmission;setting a location in time of HARQ feedback associated with the first DLdata transmission to be the same as the location in time of HARQfeedback associated with the second DL data transmission; andtransmitting the HARQ feedback associated with the first DL datatransmission at the set location in time.

According to one aspect of the present disclosure, a method, performedby a wireless device, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: receiving a first DownlinkControl Information (DCI) associated with a first Downlink (DL) datatransmission of a first PDSCH group, the first DCI comprising anumerical PDSCH-to-HARQ-timing-indicator; determining that the numericalPDSCH-to-HARQ-timing-indicator is a predefined value indicating that acorresponding Uplink (UL) HARQ transmission on a Physical Uplink ControlChannel (PUCCH) should be sent in a slot or set of symbols that can bedynamically chosen to be used for UL or DL; determining that the slot orset of symbols has been set for DL transmission and thus is unavailablefor the corresponding UL HARQ transmission; in response to thatdetermination, postponing the corresponding HARQ transmission.

In some embodiments, the method further comprises receiving a second DCIassociated with a second DL data transmission, the second DCI comprisinga numerical PDSCH-to-HARQ-timing-indicator indicating a location in timefor HARQ feedback associated with the second DL data transmission;setting a location in time of HARQ feedback associated with the first DLdata transmission to be the same as the location in time of HARQfeedback associated with the second DL data transmission; andtransmitting the HARQ feedback associated with the first DL datatransmission at the set location in time.

According to one aspect of the present disclosure, a method, performedby a wireless device, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: receiving a first DownlinkControl Information (DCI) associated with a first Downlink (DL) datatransmission, the first DCI comprising a numericalPDSCH-to-HARQ-timing-indicator having a predefined value indicating thatHARQ transmissions should be delayed until the wireless device hasreceived a DCI comprising a numerical PDSCH-to-HARQ-timing-indicatorhaving a value different from the predefined value; receiving the firstDL data transmission; determining a HARQ feedback for the first DL datatransmission; receiving a second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location in time for HARQfeedback associated with the second DL data transmission; setting alocation in time of HARQ feedback associated with the first DL datatransmission to be the same as the location in time of HARQ feedbackassociated with the second DL data transmission; and transmitting theHARQ feedback associated with the first DL data transmission at the setlocation in time.

In some embodiments, the predefined value comprises an existingPDSCH-to-HARQ-timing-indicator value that has been remapped fromindicating a delay value to indicating that HARQ transmissions should bedelayed until the wireless device has received a DCI comprising anumerical PDSCH-to-HARQ-timing-indicator having a value different fromthe predefined value.

In some embodiments, prior to receiving the first DCI, the wirelessdevice receives an instruction to remap the existingPDSCH-to-HARQ-timing-indicator value from indicating a delay value toindicating that HARQ transmissions should be delayed until the wirelessdevice has received a DCI comprising a numericalPDSCH-to-HARQ-timing-indicator having a value different from thepredefined value.

In some embodiments, the predefined value comprises an additional bitthat has been added to an existing PDSCH-to-HARQ-timing-indicator valuebit field in the DCI.

According to one aspect of the present disclosure, a method, performedby a base station, for setting Hybrid Automatic Repeat Request (HARQ)timing for Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator comprises: determining aPDSCH-to-HARQ-timing for an upcoming Downlink (DL) data transmission toa User Equipment (UE); determining that the HARQ feedback for theupcoming DL data transmission should be delayed by the UE until furthernotification from the base station; and transmitting, to the UE, a firstDownlink Control Information (DCI) associated with the upcoming DL datatransmission, the first DCI comprising a predefinedPDSCH-to-HARQ-timing-indicator value for indicating to the UE that HARQfeedback for the upcoming DL data transmission should be delayed untilfurther notification from the base station.

In some embodiments, determining that the HARQ feedback for the upcomingDL data transmission should be delayed by the UE until furthernotification from the base station comprises determining that aprocessing delay from the end of the upcoming DL data transmission tothe beginning of the HARQ feedback opportunity is less than a minimumthreshold delay.

In some embodiments, the predefined PDSCH-to-HARQ-timing-indicator valuecomprises a non-numerical value.

In some embodiments, the predefined PDSCH-to-HARQ-timing-indicator valuecomprises an existing PDSCH-to-HARQ-timing-indicator value that has beenremapped from indicating a delay value to indicating that HARQtransmissions should be delayed until a wireless device has received aDCI comprising a numerical PDSCH-to-HARQ-timing-indicator having a valuedifferent from the predefined value.

In some embodiments, prior to sending the first DCI, the base stationsends, to the UE, an instruction to remap the existingPDSCH-to-HARQ-timing-indicator value from indicating a delay value toindicating that HARQ transmissions should be delayed until the wirelessdevice has received a DCI comprising a numericalPDSCH-to-HARQ-timing-indicator having a value different from thepredefined value.

In some embodiments, the predefined PDSCH-to-HARQ-timing-indicator valuecomprises an additional bit that has been added to an existingPDSCH-to-HARQ-timing-indicator value bit field in the DCI.

In some embodiments, the method further comprises transmitting thefurther notification to the UE.

In some embodiments, transmitting the further notification to the UEcomprises transmitting a second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator.

In some embodiments, transmitting the second DCI further comprisestransmitting at least one of the following: a HARQ process Identifier(ID); a New Data Indicator (NDI) value; a PDSCH group ID; a DownlinkAssignment Indicator (DAI); or a trigger bit.

According to one aspect of the present disclosure, a wireless device forsetting Hybrid Automatic Repeat Request (HARQ) timing for PhysicalDownlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator, the wireless device comprisingprocessing circuitry configured to: receive a first Downlink ControlInformation (DCI) associated with a first Downlink (DL) datatransmission, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator; receive the first DL data transmission;determine a HARQ feedback for the first DL data transmission; receive asecond DCI associated with a second DL data transmission, the second DCIcomprising a numerical PDSCH-to-HARQ-timing-indicator indicating alocation in time for HARQ feedback associated with the second DL datatransmission; set a location in time of HARQ feedback associated withthe first DL data transmission to be the same as the location in time ofHARQ feedback associated with the second DL data transmission; andtransmit the HARQ feedback associated with the first DL datatransmission at the set location in time.

In some embodiments, the processing circuitry is further configured toperform the steps of any of the wireless device methods disclosedherein.

In some embodiments, the processing circuitry comprises one or moreprocessors and memory storing instructions executable by the one or moreprocessors whereby the wireless device is operable to perform the steps.

According to one aspect of the present disclosure, a base station forsetting Hybrid Automatic Repeat Request (HARQ) timing for PhysicalDownlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator, the base station comprising processingcircuitry configured to: determine a PDSCH-to-HARQ-timing for anupcoming Downlink (DL) data transmission to a User Equipment (UE);determine that the HARQ feedback for the upcoming DL data transmissionshould be delayed by the UE until further notification from the basestation; and transmit, to the UE, a first Downlink Control Information(DCI) associated with a first DL data transmission, the first DCIcomprising a predefined PDSCH-to-HARQ-timing-indicator value forindicating to the UE that HARQ feedback for the first DL datatransmission should be delayed until further notification from the basestation.

In some embodiments, the processing circuitry is further configured toperform the steps of any of the base station methods disclosed herein.

In some embodiments, the processing circuitry comprises one or moreprocessors and memory storing instructions executable by the one or moreprocessors whereby the wireless device is operable to perform the steps.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIG. 1 illustrates HARQ feedback according to a conventional NR system;

FIG. 2 shows one example of combined HARQ feedback according to aconventional NR system;

FIG. 3 shows another example of combined HARQ feedback according to aconventional NR system;

FIG. 4 illustrates one problem suffered by a conventional NR system;

FIG. 5 illustrates setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure;

FIG. 6 is a flow chart illustrating steps of an exemplary method forsetting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure;

FIG. 7 is a flow chart illustrating steps of an exemplary method forsetting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure;

FIG. 8 illustrates a flow chart illustrating steps of an exemplarymethod for setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure;

FIG. 9 illustrates a flow chart illustrating steps of an exemplarymethod for setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure;

FIG. 10 illustrates one example of a cellular communications system inwhich embodiments of the present disclosure may be implemented;

FIG. 11 illustrates a wireless communication system represented as a 5Gnetwork architecture composed of core Network Functions (NFs), whereinteraction between any two NFs is represented by a point-to-pointreference point/interface;

FIG. 12 illustrates a 5G network architecture using service-basedinterfaces between the NFs in the control plane, instead of thepoint-to-point reference points/interfaces used in the 5G networkarchitecture of FIG. 11;

FIG. 13 illustrates one embodiment of a UE in accordance with variousaspects described herein;

FIG. 14 is a schematic block diagram illustrating a virtualizationenvironment 1400 in which functions implemented by some embodiments maybe virtualized;

FIG. 15 illustrates a communication system according to some embodimentsof the present disclosure;

FIG. 16 illustrates a communication system according to some embodimentsof the present disclosure;

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure;

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure;

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure; and

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments and illustrate the bestmode of practicing the embodiments. Upon reading the followingdescription in light of the accompanying drawing figures, those skilledin the art will understand the concepts of the disclosure and willrecognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the disclosure.

Setting the PDSCH-to-HARQ-Timing Indicator for Pending Feedback with NonNumerical PDSCH-to-HARQ-Timing-Indicator Embodiment 1—Use Next ValidTiming Indicator

FIG. 5 illustrates setting Hybrid Automatic Repeat Request (HARQ) timingfor Physical Downlink Shared Channel (PDSCH) with a pendingPDSCH-to-HARQ-timing-indicator according to some embodiments of thepresent disclosure. In the embodiment illustrated in FIG. 5, the timingand/or the resources for the pending HARQ-Acknowledgement (ACK) feedbackare set to be the same as for the first subsequently transmitted HARQprocess with a valid (numerical) PDSCH-to-HARQ-timing-indicator. In FIG.5, for example, the HARQ timing for PDSCH 3 is set to be the samelocation in the time domain (referred to herein variously as a“location”, “location in time”, “time resource”, “time”, “occasion”,“transmission opportunity”, and the like) as that pointed to by thePDSCH-to-HARQ-timing-indicator of PDSCH 4, i.e., the location ofPhysical Uplink Control Channel (PUCCH) 2. Put another way, the HARQfeedback for PDSCH 3 and the HARQ feedback for PDSCH 4 are jointlytransmitted in the HARQ feedback opportunity indicated by the numericalPDSCH-to-HARQ-timing indicator for the HARQ feedback for PDSCH 4.

As another aspect of this embodiment, the Downlink Assignment Indicator(DAI) value for the first PDSCH with a validPDSCH-to-HARQ-timing-indicator (e.g., PDSCH 4) should also count theprevious PDSCH(s) with non-numerical PDSCH-to-HARQ-timing-indicator(e.g., PDSCH 3) since the last PDSCH with validPDSCH-to-HARQ-timing-indicator (e.g., PDSCH 2). In FIG. 5, for example,the value for ΔT within Physical Downlink Control Channel (PDCCH) 4should be 2 (representing PDSCH 3 and PDSCH 4) rather than 1(representing only PDCSH 4).

FIG. 6 is a flow chart illustrating steps of an exemplary method,performed at a User Equipment (UE), for setting HARQ timing for PDSCHwith a pending PDSCH-to-HARQ-timing-indicator according to embodiment 1of the present disclosure. In the embodiment illustrated in FIG. 6, theprocess includes the following steps:

Step 600: receive first Downlink Control Information (DCI) associatedwith a first Downlink (DL) data transmission, the first DCI comprising anon-numerical PDSCH-to-HARQ-timing-indicator;

Step 602: receive the first DL data transmission;

Step 604: determine a HARQ feedback for the first DL data transmission;

Step 606: receive second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location for HARQ feedbackassociated with the second DL data transmission;

Step 608: set the location of HARQ feedback associated with the first DLdata transmission to be the same as the location of HARQ feedbackassociated with the second DL data transmission; and

Step 610: transmit the HARQ feedback associated with the first DL datatransmission at the location set in step 608.

Embodiment 2—Also Consider PDSCH Group

In some embodiments of the present disclosure, if the DCI scheduling thePDSCH supports PDSCH group indication, the timing and/or the resourcesfor the pending HARQ-ACK feedback is set to be the same as the firstsubsequently transmitted HARQ process that belongs to the same group andwith valid (numerical) PDSCH-to-HARQ-timing-indicator.

As another aspect of this embodiment, the DAI value for the first PDSCHwith a valid PDSCH-to-HARQ-timing-indicator counts also the previousPDSCH(s) with non-numerical PDSCH-to-HARQ-timing-indicator that belongto the same PDSCH group since the last PDSCH with validPDSCH-to-HARQ-timing-indicator.

FIG. 7 is a flow chart illustrating steps of an exemplary method,performed at a UE, for setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator according to embodiment 2 of the presentdisclosure. In the embodiment illustrated in FIG. 7, the processincludes the following steps:

Step 700: receive first DCI associated with a first DL data transmissionof a first PDSCH group, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator;

Step 702: receive the first DL data transmission;

Step 704: determine a HARQ feedback for the first DL data transmission;

Step 706: receive second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location for HARQ feedbackassociated with the second DL data transmission;

Step 708: determine if the second DL data transmission is of the samePDSCH group as the first DL data transmission. If not, end the process.If so, go to step 710.

Step 710: set the location of HARQ feedback associated with the first DLdata transmission to be the same as the location of HARQ feedbackassociated with the second DL data transmission; and

Step 712: transmit the HARQ feedback associated with the first DL datatransmission at the location set in step 710.

Embodiment 3—Explicit DCI Signaling

In some embodiments of the present disclosure, a new signaling isdefined to indicate timing and the resources for the pending HARQ-ACKfeedback (with non-numerical timing indication). For example, in someembodiments, a new UE-specific DCI is transmitted on the PDCCH. Examplesinclude, but are not limited to, the following:

-   -   The DCI indicates at least the HARQ process Identifier(s)        (ID(s)) and the PDSCH-to-HARQ-timing-indicator. It might also        include New Data Indicator (NDI) values corresponding to the        HARQ process ID(s).    -   The DCI indicates at least the PDSCH group ID(s), corresponding        DAI, and the PDSCH-PDSCH-to-HARQ-timing-indicator.    -   The DCI includes a trigger bit, and the        PDSCH-to-HARQ-timing-indicator which is applicable to all the        PDSCH(s) with a pending or unset PDSCH-to-HARQ-timing-indicator.        -   In some embodiments, the trigger can be part of a DCI that            is scheduling another PDSCH. In some embodiments, the            PDSCH-to-HARQ-timing-indicator is applicable to the pending            and the new PDSCH.        -   In some embodiments, the trigger can be part of a separate            DCI that does not schedule PDSCH.

FIG. 8 illustrates a flow chart illustrating steps of an exemplarymethod, performed at a New Radio (NR) base station (gNB), for settingHARQ timing for PDSCH with a pending PDSCH-to-HARQ-timing-indicatoraccording to embodiment 3 of the present disclosure. In the embodimentillustrated in FIG. 8, the process includes the following steps:

Step 800: transmit, to a first UE, a first DCI associated with a firstDL data transmission, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator;

Step 802: transmit, to the first UE, a second DCI associated with asecond DL data transmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator and at least one of the following: atleast one HARQ process ID; a NDI value; at least one PDSCH group ID; acorresponding DAI; and/or a trigger bit.

Embodiment 4—Delayed HARQ Despite Numerical Timing Indicator

In some embodiments of the present disclosure, according to predefinedrules (e.g., Radio Resource Control (RRC) configuration), the UE is notexpected to send the feedback according to the indicated numerical K1value and is expected to postpone sending the feedback until new timingand resource for the HARQ-ACK feedback is provided by the gNB. Exampleconditions include, but are not limited to, the following:

Condition 1: The PDSCHs scheduled with a numeric K1 value, resulting ina HARQ-ACK transmission that is too close to a PUCCH to be sent on thePUCCH, e.g., because the required processing time between the end of thePDSCH and the PUCCH cannot be met.

-   -   In some embodiments, the gNB detects the condition from the lack        of HARQ feedback in the indicated PUCCH resource; this can        trigger the gNB to signal new HARQ feedback timing, e.g., in        accordance with one of the embodiment 3 alternatives, or in a        subsequent DCI in accordance with embodiment 2. Yet another        alternative is that embodiment 1 is used, in which case the gNB        does not have to take any explicit signaling action to resolve        the situation, but will have to be prepared to receive the HARQ        feedback in accordance with embodiment 1.    -   In some embodiments, as an alternative to using lack of HARQ        feedback as a sign of delayed HARQ feedback, the UE, when the        processing time is too short for providing “real” HARQ feedback,        instead provides an indication (on the PUCCH indicated by the        numerical K1) which informs the gNB that the UE has postponed        the HARQ feedback (e.g., because of lack of processing time).        This would be a new type of indication to be standardized.

Condition 2: The PDSCHs scheduled with a numeric K1 value, that thecorresponding HARQ-ACK transmission on a PUCCH should be postponed, dueto a later request for another HARQ-ACK transmission on a PUCCHcorresponding to another PDSCH(s)

Condition 3: A PDSCH is scheduled with a numerical K1 value, indicatingthat HARQ feedback should be sent in a dynamic slot or a set of dynamicsymbols (i.e., symbols that can be used for either Uplink (UL) or DLtransmissions as dynamically chosen by the gNB), and the gNB laterallocates these symbols (or this slot) for DL transmission. In thiscase, the postponed HARQ feedback can be handled in accordance withembodiment 3, 2 or 1 in the same ways as described above for condition1.

FIG. 9 illustrates a flow chart illustrating steps of an exemplarymethod, performed at a UE, for setting HARQ timing for PDSCH with apending PDSCH-to-HARQ-timing-indicator according to embodiment 4,condition 1, of the present disclosure. In the embodiment illustrated inFIG. 9, the process includes the following steps:

Step 900: receive first DCI associated with a first DL data transmissionof a first PDSCH group, the first DCI comprising a numericalPDSCH-to-HARQ-timing-indicator;

Step 902: determine that the location for the HARQ that is associatedwith the first dl data transmission, indicated by the numericalPDSCH-to-HARQ-timing-indicator, is too close to the first DL datatransmission; and

Step 904: in response to that determination, do not transmit the HARQthat is associated with the first DL data transmission at the indicatedHARQ transmission time;

Step 906: optionally, provide an indication, on the PUCCH at theindicated HARQ transmission time, which informs the gNB that the HARQfeedback was postponed.

Embodiment 5—Modified or Extended PDSCH-to-HARQ-Timing-Indicator Field

In some embodiments of the present disclosure, the exitingPDSCH-to-HARQ-timing-indicator field in NR Release (Rel-) 15 is modifiedor extended. Example embodiments include, but are not limited to, thefollowing:

In one embodiment, the DCI format 1_0, thePDSCH-to-HARQ-timing-indicator field in NR Rel-15 is 3 bits with valuesmapping to {1, 2, 3, 4, 5, 6, 7, 8} in number of slots, but for the NR-Uuse case, the field is extended by 1 bit, providing 16 possible HARQfeedback timing offset values. One of the 16 values (e.g. 0b1111) can beused as non-numerical value to indicate pending HARQ feedbacktransmission until further notice, and the remaining 15 values can beused to provide further HARQ feedback scheduling flexibility.

In an alternative embodiment, the PDSCH-to-HARQ-timing-indicator remainsat 3 bits, but one of the current values (e.g. 0b111) is redefined asnon-numerical for NR-U to indicate pending HARQ feedback transmissionuntil further notice.

In either of the embodiments described above, the modification orextension of the PDSCH-to-HARQ-timing-indicator field and/or there-interpretation of one of the values to the non-numerical value can beconfigurable by higher layers.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 10.

FIG. 10 illustrates one example of a cellular communications system 1000in which embodiments of the present disclosure may be implemented. Forsimplicity, the wireless network of FIG. 10 only depicts a network 1006,network nodes 1060 and 1060B, and Wireless Devices (WDs) 1010, 1010B,and 1010C. In practice, a wireless network may further include anyadditional elements suitable to support communication between wirelessdevices or between a wireless device and another communication device,such as a landline telephone, a service provider, or any other networknode or end device. Of the illustrated components, the network node 1060and the WD 1010 are depicted with additional detail. The wirelessnetwork may provide communication and other types of services to one ormore wireless devices to facilitate the wireless devices' access toand/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation(2G, 3G, 4G, or 5G) standards; Wireless Local Area Network (WLAN)standards, such as the IEEE 802.11 standards; and/or any otherappropriate wireless communication standard, such as the WorldwideInteroperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and/orZigBee standards.

The network 1006 may comprise one or more backhaul networks, corenetworks, Internet Protocol (IP) networks, Public Switched TelephoneNetworks (PSTNs), packet data networks, optical networks, Wide AreaNetworks (WANs), Local Area Networks (LANs), WLANs, wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

The network node 1060 and the WD 1010 comprise various componentsdescribed in more detail below. These components work together in orderto provide network node and/or wireless device functionality, such asproviding wireless connections in a wireless network. In differentembodiments, the wireless network may comprise any number of wired orwireless networks, network nodes, base stations, controllers, wirelessdevices, relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged, and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, Access Points (APs) (e.g., radio APs), Base Stations (BSs)(e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NewRadio (NR) base stations (gNBs)). Base stations may be categorized basedon the amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or Remote Radio Units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such RRUs may or may not be integrated withan antenna as an antenna integrated radio. Parts of a distributed radiobase station may also be referred to as nodes in a Distributed AntennaSystem (DAS). Yet further examples of network nodes includeMulti-Standard Radio (MSR) equipment such as MSR BSs, networkcontrollers such as Radio Network Controllers (RNCs) or BS Controllers(BSCs), Base Transceiver Stations (BTSs), transmission points,transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs),core network nodes (e.g., Mobile Switching Centers (MSCs), MobilityManagement Entities (MMEs)), Operation and Maintenance (O&M) nodes,Operations Support System (OSS) nodes, Self-Organizing Network (SON)nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center(E-SMLCs)), and/or Minimization of Drive Tests (MDTs). As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 10, the network node 1060 includes processing circuitry 1070, adevice readable medium 1080, an interface 1090, auxiliary equipment1084, a power source 1086, power circuitry 1087, and an antenna 1062.Although the network node 1060 illustrated in the example wirelessnetwork of FIG. 10 may represent a device that includes the illustratedcombination of hardware components, some embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions, and methods disclosed herein. Moreover, while the componentsof the network node 1060 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., the device readable medium 1080 maycomprise multiple separate hard drives as well as multiple Random AccessMemory (RAM) modules).

Similarly, the network node 1060 may be composed of multiple physicallyseparate components (e.g., a Node B component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which the network node1060 comprises multiple separate components (e.g., BTS and BSCcomponents), one or more of the separate components may be shared amongseveral network nodes. For example, a single RNC may control multipleNode Bs. In such a scenario, each unique Node B and RNC pair may in someinstances be considered a single separate network node. In someembodiments, the network node 1060 may be configured to support multipleRadio Access Technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., a separate device readable medium 1080 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 1062 may be shared by the RATs). The network node 1060 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into the network node 1060,such as, for example, GSM, Wideband Code Division Multiple Access(WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies. Thesewireless technologies may be integrated into the same or a differentchip or set of chips and other components within the network node 1060.

The processing circuitry 1070 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by the processing circuitry 1070 may include processinginformation obtained by the processing circuitry 1070 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

The processing circuitry 1070 may comprise a combination of one or moreof a microprocessor, a controller, a microcontroller, a CentralProcessing Unit (CPU), a Digital Signal Processor (DSP), an ApplicationSpecific Integrated Circuit (ASIC), a Field Programmable Gate Array(FPGA), or any other suitable computing device, resource, or combinationof hardware, software, and/or encoded logic operable to provide, eitheralone or in conjunction with other network node 1060 components, such asthe device readable medium 1080, network node 1060 functionality. Forexample, the processing circuitry 1070 may execute instructions storedin the device readable medium 1080 or in memory within the processingcircuitry 1070. Such functionality may include providing any of thevarious wireless features, functions, or benefits discussed herein. Insome embodiments, the processing circuitry 1070 may include a System ona Chip (SOC).

In some embodiments, the processing circuitry 1070 may include one ormore of Radio Frequency (RF) transceiver circuitry 1072 and basebandprocessing circuitry 1074. In some embodiments, the RF transceivercircuitry 1072 and the baseband processing circuitry 1074 may be onseparate chips (or sets of chips), boards, or units, such as radio unitsand digital units. In alternative embodiments, part or all of the RFtransceiver circuitry 1072 and the baseband processing circuitry 1074may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB, or othersuch network device may be performed by the processing circuitry 1070executing instructions stored on the device readable medium 1080 ormemory within the processing circuitry 1070. In alternative embodiments,some or all of the functionality may be provided by the processingcircuitry 1070 without executing instructions stored on a separate ordiscrete device readable medium, such as in a hard-wired manner. In anyof those embodiments, whether executing instructions stored on a devicereadable storage medium or not, the processing circuitry 1070 can beconfigured to perform the described functionality. The benefits providedby such functionality are not limited to the processing circuitry 1070alone or to other components of the network node 1060, but are enjoyedby the network node 1060 as a whole, and/or by end users and thewireless network generally.

The device readable medium 1080 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid state memory, remotely mounted memory,magnetic media, optical media, RAM, Read Only Memory (ROM), mass storagemedia (for example, a hard disk), removable storage media (for example,a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)),and/or any other volatile or non-volatile, non-transitory devicereadable and/or computer-executable memory devices that storeinformation, data, and/or instructions that may be used by theprocessing circuitry 1070. The device readable medium 1080 may store anysuitable instructions; data or information, including a computerprogram; software; an application including one or more of logic, rules,code, tables, etc.; and/or other instructions capable of being executedby the processing circuitry 1070 and utilized by the network node 1060.The device readable medium 1080 may be used to store any calculationsmade by the processing circuitry 1070 and/or any data received via theinterface 1090. In some embodiments, the processing circuitry 1070 andthe device readable medium 1080 may be considered to be integrated.

The interface 1090 is used in the wired or wireless communication ofsignaling and/or data between the network node 1060, a network 1006,and/or WDs 1010. As illustrated, the interface 1090 comprisesport(s)/terminal(s) 1094 to send and receive data, for example to andfrom the network 1006 over a wired connection. The interface 1090 alsoincludes radio front end circuitry 1092 that may be coupled to, or incertain embodiments a part of, the antenna 1062. The radio front endcircuitry 1092 comprises filters 1098 and amplifiers 1096. The radiofront end circuitry 1092 may be connected to the antenna 1062 and theprocessing circuitry 1070. The radio front end circuitry 1092 may beconfigured to condition signals communicated between the antenna 1062and the processing circuitry 1070. The radio front end circuitry 1092may receive digital data that is to be sent out to other network nodesor WDs via a wireless connection. The radio front end circuitry 1092 mayconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of the filters 1098and/or the amplifiers 1096. The radio signal may then be transmitted viathe antenna 1062. Similarly, when receiving data, the antenna 1062 maycollect radio signals which are then converted into digital data by theradio front end circuitry 1092. The digital data may be passed to theprocessing circuitry 1070. In some embodiments, the interface 1090 maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, the network node 1060 may notinclude separate radio front end circuitry 1092; instead, the processingcircuitry 1070 may comprise radio front end circuitry and may beconnected to the antenna 1062 without separate radio front end circuitry1092. Similarly, in some embodiments, all or some of the RF transceivercircuitry 1072 may be considered a part of the interface 1090. In stillsome embodiments, the interface 1090 may include the one or more portsor terminals 1094, the radio front end circuitry 1092, and the RFtransceiver circuitry 1072 as part of a radio unit (not shown), and theinterface 1090 may communicate with the baseband processing circuitry1074, which is part of a digital unit (not shown).

The antenna 1062 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. The antenna 1062 maybe coupled to the radio front end circuitry 1092 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, the antenna 1062 may comprise one ormore omni-directional, sector, or panel antennas operable totransmit/receive radio signals between, for example, 2 gigahertz (GHz)and 66 GHz. An omni-directional antenna may be used to transmit/receiveradio signals in any direction, a sector antenna may be used totransmit/receive radio signals from devices within a particular area,and a panel antenna may be a line of sight antenna used totransmit/receive radio signals in a relatively straight line. In someinstances, the use of more than one antenna may be referred to asMultiple Input Multiple Output (MIMO). In certain embodiments, theantenna 1062 may be separate from the network node 1060 and may beconnectable to the network node 1060 through an interface or port.

The antenna 1062, the interface 1090, and/or the processing circuitry1070 may be configured to perform any receiving operations and/orcertain obtaining operations described herein as being performed by anetwork node. Any information, data, and/or signals may be received froma WD, another network node, and/or any other network equipment.Similarly, the antenna 1062, the interface 1090, and/or the processingcircuitry 1070 may be configured to perform any transmitting operationsdescribed herein as being performed by a network node. Any information,data, and/or signals may be transmitted to a WD, another network node,and/or any other network equipment.

The power circuitry 1087 may comprise, or be coupled to, powermanagement circuitry and is configured to supply the components of thenetwork node 1060 with power for performing the functionality describedherein. The power circuitry 1087 may receive power from the power source1086. The power source 1086 and/or the power circuitry 1087 may beconfigured to provide power to the various components of the networknode 1060 in a form suitable for the respective components (e.g., at avoltage and current level needed for each respective component). Thepower source 1086 may either be included in, or be external to, thepower circuitry 1087 and/or the network node 1060. For example, thenetwork node 1060 may be connectable to an external power source (e.g.,an electricity outlet) via an input circuitry or interface such as anelectrical cable, whereby the external power source supplies power tothe power circuitry 1087. As a further example, the power source 1086may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, the power circuitry 1087. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of the network node 1060 may include additionalcomponents beyond those shown in FIG. 10 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,the network node 1060 may include user interface equipment to allowinput of information into the network node 1060 and to allow output ofinformation from the network node 1060. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions forthe network node 1060.

As used herein, WD refers to a device capable, configured, arranged,and/or operable to communicate wirelessly with network nodes and/orother WDs. Unless otherwise noted, the term WD may be usedinterchangeably herein with User Equipment (UE). Communicatingwirelessly may involve transmitting and/or receiving wireless signalsusing electromagnetic waves, radio waves, infrared waves, and/or othertypes of signals suitable for conveying information through air. In someembodiments, a WD may be configured to transmit and/or receiveinformation without direct human interaction. For instance, a WD may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the network. Examples of a WD include, but arenot limited to, a smart phone, a mobile phone, a cell phone, a Voiceover IP (VoIP) phone, a wireless local loop phone, a desktop computer, aPersonal Digital Assistant (PDA), a wireless camera, a gaming console ordevice, a music storage device, a playback appliance, a wearableterminal device, a wireless endpoint, a mobile station, a tablet, alaptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME),a smart device, a wireless Customer Premise Equipment (CPE), a vehiclemounted wireless terminal device, etc. A WD may support Device-to-Device(D2D) communication, for example by implementing a 3G PartnershipProject (3GPP) standard for sidelink communication, Vehicle-to-Vehicle(V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Everything (V2X), andmay in this case be referred to as a D2D communication device. As yetanother specific example, in an Internet of Things (IoT) scenario, a WDmay represent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a Machine-to-Machine (M2M) device, which may in a 3GPP contextbe referred to as a Machine-Type Communication (MTC) device. As oneparticular example, the WD may be a UE implementing the 3GPP NarrowbandIoT (NB-IoT) standard. Particular examples of such machines or devicesare sensors, metering devices such as power meters, industrialmachinery, home or personal appliances (e.g., refrigerators,televisions, etc.), or personal wearables (e.g., watches, fitnesstrackers, etc.). In other scenarios, a WD may represent a vehicle orother equipment that is capable of monitoring and/or reporting on itsoperational status or other functions associated with its operation. AWD as described above may represent the endpoint of a wirelessconnection, in which case the device may be referred to as a wirelessterminal. Furthermore, a WD as described above may be mobile, in whichcase it may also be referred to as a mobile device or a mobile terminal.

As illustrated in FIG. 10, a WD 1010 includes an antenna 1011, aninterface 1014, processing circuitry 1020, a device readable medium1030, user interface equipment 1032, auxiliary equipment 1034, a powersource 1036, and power circuitry 1037. The WD 1010 may include multiplesets of one or more of the illustrated components for different wirelesstechnologies supported by the WD 1010, such as, for example, GSM, WCDMA,LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just tomention a few. These wireless technologies may be integrated into thesame or different chips or set of chips as other components within theWD 1010.

The antenna 1011 may include one or more antennas or antenna arraysconfigured to send and/or receive wireless signals and is connected tothe interface 1014. In certain alternative embodiments, the antenna 1011may be separate from the WD 1010 and be connectable to the WD 1010through an interface or port. The antenna 1011, the interface 1014,and/or the processing circuitry 1020 may be configured to perform anyreceiving or transmitting operations described herein as being performedby a WD. Any information, data, and/or signals may be received from anetwork node and/or another WD. In some embodiments, radio front endcircuitry and/or the antenna 1011 may be considered an interface.

As illustrated, the interface 1014 comprises radio front end circuitry1012 and the antenna 1011. The radio front end circuitry 1012 comprisesone or more filters 1018 and amplifiers 1016. The radio front endcircuitry 1012 is connected to the antenna 1011 and the processingcircuitry 1020 and is configured to condition signals communicatedbetween the antenna 1011 and the processing circuitry 1020. The radiofront end circuitry 1012 may be coupled to or be a part of the antenna1011. In some embodiments, the WD 1010 may not include separate radiofront end circuitry 1012; rather, the processing circuitry 1020 maycomprise radio front end circuitry and may be connected to the antenna1011. Similarly, in some embodiments, some or all of RF transceivercircuitry 1022 may be considered a part of the interface 1014. The radiofront end circuitry 1012 may receive digital data that is to be sent outto other network nodes or WDs via a wireless connection. The radio frontend circuitry 1012 may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters using acombination of the filters 1018 and/or the amplifiers 1016. The radiosignal may then be transmitted via the antenna 1011. Similarly, whenreceiving data, the antenna 1011 may collect radio signals which arethen converted into digital data by the radio front end circuitry 1012.The digital data may be passed to the processing circuitry 1020. In someembodiments, the interface 1014 may comprise different components and/ordifferent combinations of components.

The processing circuitry 1020 may comprise a combination of one or moreof a microprocessor, a controller, a microcontroller, a CPU, a DSP, anASIC, a FPGA, or any other suitable computing device, resource, orcombination of hardware, software, and/or encoded logic operable toprovide, either alone or in conjunction with other WD 1010 components,such as the device readable medium 1030, WD 1010 functionality. Suchfunctionality may include providing any of the various wireless featuresor benefits discussed herein. For example, the processing circuitry 1020may execute instructions stored in the device readable medium 1030 or inmemory within the processing circuitry 1020 to provide the functionalitydisclosed herein.

As illustrated, the processing circuitry 1020 includes one or more ofthe RF transceiver circuitry 1022, baseband processing circuitry 1024,and application processing circuitry 1026. In some embodiments, theprocessing circuitry 1020 may comprise different components and/ordifferent combinations of components. In certain embodiments, theprocessing circuitry 1020 of the WD 1010 may comprise a SOC. In someembodiments, the RF transceiver circuitry 1022, the baseband processingcircuitry 1024, and the application processing circuitry 1026 may be onseparate chips or sets of chips. In alternative embodiments, part or allof the baseband processing circuitry 1024 and the application processingcircuitry 1026 may be combined into one chip or set of chips, and the RFtransceiver circuitry 1022 may be on a separate chip or set of chips. Instill alternative embodiments, part or all of the RF transceivercircuitry 1022 and the baseband processing circuitry 1024 may be on thesame chip or set of chips, and the application processing circuitry 1026may be on a separate chip or set of chips. In yet other alternativeembodiments, part or all of the RF transceiver circuitry 1022, thebaseband processing circuitry 1024, and the application processingcircuitry 1026 may be combined in the same chip or set of chips. In someembodiments, the RF transceiver circuitry 1022 may be a part of theinterface 1014. The RF transceiver circuitry 1022 may condition RFsignals for the processing circuitry 1020.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by the processingcircuitry 1020 executing instructions stored on the device readablemedium 1030, which in certain embodiments may be a computer-readablestorage medium. In alternative embodiments, some or all of thefunctionality may be provided by the processing circuitry 1020 withoutexecuting instructions stored on a separate or discrete device readablestorage medium, such as in a hard-wired manner. In any of thoseparticular embodiments, whether executing instructions stored on adevice readable storage medium or not, the processing circuitry 1020 canbe configured to perform the described functionality. The benefitsprovided by such functionality are not limited to the processingcircuitry 1020 alone or to other components of the WD 1010, but areenjoyed by the WD 1010 as a whole, and/or by end users and the wirelessnetwork generally.

The processing circuitry 1020 may be configured to perform anydetermining, calculating, or similar operations (e.g., certain obtainingoperations) described herein as being performed by a WD. Theseoperations, as performed by the processing circuitry 1020, may includeprocessing information obtained by the processing circuitry 1020 by, forexample, converting the obtained information into other information,comparing the obtained information or converted information toinformation stored by the WD 1010, and/or performing one or moreoperations based on the obtained information or converted information,and as a result of said processing making a determination.

The device readable medium 1030 may be operable to store a computerprogram; software; an application including one or more of logic, rules,code, tables, etc.; and/or other instructions capable of being executedby the processing circuitry 1020. The device readable medium 1030 mayinclude computer memory (e.g., RAM or ROM), mass storage media (e.g., ahard disk), removable storage media (e.g., a CD or a DVD), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by the processing circuitry 1020. In someembodiments, the processing circuitry 1020 and the device readablemedium 1030 may be considered to be integrated.

The user interface equipment 1032 may provide components that allow fora human user to interact with the WD 1010. Such interaction may be ofmany forms, such as visual, audial, tactile, etc. The user interfaceequipment 1032 may be operable to produce output to the user and toallow the user to provide input to the WD 1010. The type of interactionmay vary depending on the type of user interface equipment 1032installed in the WD 1010. For example, if the WD 1010 is a smart phone,the interaction may be via a touch screen; if the WD 1010 is a smartmeter, the interaction may be through a screen that provides usage(e.g., the number of gallons used) or a speaker that provides an audiblealert (e.g., if smoke is detected). The user interface equipment 1032may include input interfaces, devices and circuits, and outputinterfaces, devices and circuits. The user interface equipment 1032 isconfigured to allow input of information into the WD 1010, and isconnected to the processing circuitry 1020 to allow the processingcircuitry 1020 to process the input information. The user interfaceequipment 1032 may include, for example, a microphone, a proximity orother sensor, keys/buttons, a touch display, one or more cameras, aUniversal Serial Bus (USB) port, or other input circuitry. The userinterface equipment 1032 is also configured to allow output ofinformation from the WD 1010 and to allow the processing circuitry 1020to output information from the WD 1010. The user interface equipment1032 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits ofthe user interface equipment 1032, the WD 1010 may communicate with endusers and/or the wireless network, and allow them to benefit from thefunctionality described herein.

The auxiliary equipment 1034 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications, etc. The inclusion and type of components of theauxiliary equipment 1034 may vary depending on the embodiment and/orscenario.

The power source 1036 may, in some embodiments, be in the form of abattery or battery pack. Other types of power sources, such as anexternal power source (e.g., an electricity outlet), photovoltaicdevices, or power cells may also be used. The WD 1010 may furthercomprise the power circuitry 1037 for delivering power from the powersource 1036 to the various parts of the WD 1010 which need power fromthe power source 1036 to carry out any functionality described orindicated herein. The power circuitry 1037 may in certain embodimentscomprise power management circuitry. The power circuitry 1037 mayadditionally or alternatively be operable to receive power from anexternal power source, in which case the WD 1010 may be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. The powercircuitry 1037 may also in certain embodiments be operable to deliverpower from an external power source to the power source 1036. This maybe, for example, for the charging of the power source 1036. The powercircuitry 1037 may perform any formatting, converting, or othermodification to the power from the power source 1036 to make the powersuitable for the respective components of the WD 1010 to which power issupplied.

FIG. 11 illustrates a wireless communication system represented as a 5Gnetwork architecture composed of core Network Functions (NFs), whereinteraction between any two NFs is represented by a point-to-pointreference point/interface. FIG. 11 can be viewed as one particularimplementation of the system 1000 of FIG. 10.

Seen from the access side the 5G network architecture shown in FIG. 11comprises a plurality of User Equipment (UEs) connected to either aRadio Access Network (RAN) or an Access Network (AN) as well as anAccess and Mobility Management Function (AMF). Typically, the R(AN)comprises base stations, e.g., such as evolved Node Bs (eNBs) or NR basestations (gNBs) or similar. Seen from the core network side, the 5G coreNFs shown in FIG. 11 include a Network Slice Selection Function (NSSF),an Authentication Server Function (AUSF), a Unified Data Management(UDM), an AMF, a Session Management Function (SMF), a Policy ControlFunction (PCF), and an Application Function (AF).

Reference point representations of the 5G network architecture are usedto develop detailed call flows in the normative standardization. The N1reference point is defined to carry signaling between the UE and AMF.The reference points for connecting between the AN and AMF and betweenthe AN and UPF are defined as N2 and N3, respectively. There is areference point, N11, between the AMF and SMF, which implies that theSMF is at least partly controlled by the AMF. N4 is used by the SMF andUPF so that the UPF can be set using the control signal generated by theSMF, and the UPF can report its state to the SMF. N9 is the referencepoint for the connection between different UPFs, and N14 is thereference point connecting between different AMFs, respectively. N15 andN7 are defined since the PCF applies policy to the AMF and SMP,respectively. N12 is required for the AMF to perform authentication ofthe UE. N8 and N10 are defined because the subscription data of the UEis required for the AMF and SMF.

The 5G core network aims at separating user plane and control plane. Theuser plane carries user traffic while the control plane carriessignaling in the network. In FIG. 11, the UPF is in the user plane andall other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in thecontrol plane. Separating the user and control planes guarantees eachplane resource to be scaled independently. It also allows UPFs to bedeployed separately from control plane functions in a distributedfashion. In this architecture, UPFs may be deployed very close to UEs toshorten the Round Trip Time (RTT) between UEs and data network for someapplications requiring low latency.

The core 5G network architecture is composed of modularized functions.For example, the AMF and SMF are independent functions in the controlplane. Separated AMF and SMF allow independent evolution and scaling.Other control plane functions like the PCF and AUSF can be separated asshown in FIG. 11. Modularized function design enables the 5G corenetwork to support various services flexibly.

Each NF interacts with another NF directly. It is possible to useintermediate functions to route messages from one NF to another NF. Inthe control plane, a set of interactions between two NFs is defined asservice so that its reuse is possible. This service enables support formodularity. The user plane supports interactions such as forwardingoperations between different UPFs.

FIG. 12 illustrates a 5G network architecture using service-basedinterfaces between the NFs in the control plane, instead of thepoint-to-point reference points/interfaces used in the 5G networkarchitecture of FIG. 11. However, the NFs described above with referenceto FIG. 11 correspond to the NFs shown in FIG. 12. The service(s) etc.that a NF provides to other authorized NFs can be exposed to theauthorized NFs through the service-based interface. In FIG. 12 theservice based interfaces are indicated by the letter “N” followed by thename of the NF, e.g., Namf for the service based interface of the AMFand Nsmf for the service based interface of the SMF etc. The NetworkExposure Function (NEF) and the Network Repository Function (NRF) inFIG. 12 are not shown in FIG. 11 discussed above. However, it should beclarified that all NFs depicted in FIG. 11 can interact with the NEF andthe NRF of FIG. 12 as necessary, though not explicitly indicated in FIG.11.

Some properties of the NFs shown in FIGS. 11 and 12 may be described inthe following manner. The AMF provides UE-based authentication,authorization, mobility management, etc. A UE even using multiple accesstechnologies is basically connected to a single AMF because the AMF isindependent of the access technologies. The SMF is responsible forsession management and allocates Internet Protocol (IP) addresses toUEs. It also selects and controls the UPF for data transfer. If a UE hasmultiple sessions, different SMFs may be allocated to each session tomanage them individually and possibly provide different functionalitiesper session. The AF provides information on the packet flow to the PCFresponsible for policy control in order to support Quality of Service(QoS). Based on the information, the PCF determines policies aboutmobility and session management to make the AMF and SMF operateproperly. The AUSF supports authentication function for UEs or similarand thus stores data for authentication of UEs or similar while the UDMstores subscription data of the UE. The Data Network (DN), not part ofthe 5G core network, provides Internet access or operator services andsimilar.

An NF may be implemented either as a network element on a dedicatedhardware, as a software instance running on a dedicated hardware, or asa virtualized function instantiated on an appropriate platform, e.g., acloud infrastructure.

FIG. 13 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). A UE 1300 may be any UE identifiedby 3GPP, including a NB-IoT UE, a MTC UE, and/or an enhanced MTC (eMTC)UE. The UE 1300, as illustrated in FIG. 13, is one example of a WDconfigured for communication in accordance with one or morecommunication standards promulgated by 3GPP, such as 3GPP's GSM, UMTS,LTE, and/or 5G standards. As mentioned previously, the term WD and UEmay be used interchangeable. Accordingly, although FIG. 13 is a UE, thecomponents discussed herein are equally applicable to a WD, andvice-versa.

In FIG. 13, the UE 1300 includes processing circuitry 1301 that isoperatively coupled to an input/output interface 1305, an RF interface1309, a network connection interface 1311, memory 1315 including RAM1317, ROM 1319, and a storage medium 1321 or the like, a communicationsubsystem 1331, a power source 1313, and/or any other component, or anycombination thereof. The storage medium 1321 includes an operatingsystem 1323, an application program 1325, and data 1327. In someembodiments, the storage medium 1321 may include other similar types ofinformation. Certain UEs may utilize all of the components shown in FIG.13, or only a subset of the components. The level of integration betweenthe components may vary from one UE to another UE. Further, certain UEsmay contain multiple instances of a component, such as multipleprocessors, memories, transceivers, transmitters, receivers, etc.

In FIG. 13, the processing circuitry 1301 may be configured to processcomputer instructions and data. The processing circuitry 1301 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored programs, generalpurpose processors, such as a microprocessor or DSP, together withappropriate software; or any combination of the above. For example, theprocessing circuitry 1301 may include two CPUs. Data may be informationin a form suitable for use by a computer.

In the depicted embodiment, the input/output interface 1305 may beconfigured to provide a communication interface to an input device,output device, or input and output device. The UE 1300 may be configuredto use an output device via the input/output interface 1305. An outputdevice may use the same type of interface port as an input device. Forexample, a USB port may be used to provide input to and output from theUE 1300. The output device may be a speaker, a sound card, a video card,a display, a monitor, a printer, an actuator, an emitter, a smartcard,another output device, or any combination thereof. The UE 1300 may beconfigured to use an input device via the input/output interface 1305 toallow a user to capture information into the UE 1300. The input devicemay include a touch-sensitive or presence-sensitive display, a camera(e.g., a digital camera, a digital video camera, a web camera, etc.), amicrophone, a sensor, a mouse, a trackball, a directional pad, atrackpad, a scroll wheel, a smartcard, and the like. Thepresence-sensitive display may include a capacitive or resistive touchsensor to sense input from a user. A sensor may be, for instance, anaccelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device may bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 13, the RF interface 1309 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. The network connection interface 1311 may beconfigured to provide a communication interface to a network 1343A. Thenetwork 1343A may encompass wired and/or wireless networks such as aLAN, a WAN, a computer network, a wireless network, a telecommunicationsnetwork, another like network or any combination thereof. For example,the network 1343A may comprise a WiFi network. The network connectioninterface 1311 may be configured to include a receiver and a transmitterinterface used to communicate with one or more other devices over acommunication network according to one or more communication protocols,such as Ethernet, Transmission Control Protocol (TCP)/IP, SynchronousOptical Networking (SONET), Asynchronous Transfer Mode (ATM), or thelike. The network connection interface 1311 may implement receiver andtransmitter functionality appropriate to the communication network links(e.g., optical, electrical, and the like). The transmitter and receiverfunctions may share circuit components, software, or firmware, oralternatively may be implemented separately.

The RAM 1317 may be configured to interface via a bus 1302 to theprocessing circuitry 1301 to provide storage or caching of data orcomputer instructions during the execution of software programs such asthe operating system, application programs, and device drivers. The ROM1319 may be configured to provide computer instructions or data to theprocessing circuitry 1301. For example, the ROM 1319 may be configuredto store invariant low-level system code or data for basic systemfunctions such as basic Input and Output (I/O), startup, or reception ofkeystrokes from a keyboard that are stored in a non-volatile memory. TheStorage medium 1321 may be configured to include memory such as RAM,ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM(EEPROM), magnetic disks, optical disks, floppy disks, hard disks,removable cartridges, or flash drives. In one example, the storagemedium 1321 may be configured to include the operating system 1323, theapplication program 1325 such as a web browser application, a widget orgadget engine, or another application, and the data file 1327. Thestorage medium 1321 may store, for use by the UE 1300, any of a varietyof various operating systems or combinations of operating systems.

The storage medium 1321 may be configured to include a number ofphysical drive units, such as a Redundant Array of Independent Disks(RAID), a floppy disk drive, flash memory, a USB flash drive, anexternal hard disk drive, a thumb drive, a pen drive, a key drive, aHigh-Density Digital Versatile Disc (HD-DVD) optical disc drive, aninternal hard disk drive, a Blu-Ray optical disc drive, a HolographicDigital Data Storage (HDDS) optical disc drive, an external mini-DualIn-Line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), externalmicro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module(SIM) or a Removable User Identity (RUIM) module, other memory, or anycombination thereof. The storage medium 1321 may allow the UE 1300 toaccess computer-executable instructions, application programs, or thelike, stored on transitory or non-transitory memory media, to off-loaddata or to upload data. An article of manufacture, such as one utilizinga communication system, may be tangibly embodied in the storage medium1321, which may comprise a device readable medium.

In FIG. 13, the processing circuitry 1301 may be configured tocommunicate with a network 1343B using the communication subsystem 1331.The network 1343A and the network 1343B may be the same network ornetworks or different network or networks. The communication subsystem1331 may be configured to include one or more transceivers used tocommunicate with the network 1343B. For example, the communicationsubsystem 1331 may be configured to include one or more transceiversused to communicate with one or more remote transceivers of anotherdevice capable of wireless communication such as another WD, UE, or basestation of a Radio Access Network (RAN) according to one or morecommunication protocols, such as IEEE 802.13, Code Division MultipleAccess (CDMA), WCDMA, GSM, LTE, Universal Terrestrial RAN (UTRAN),WiMax, or the like. Each transceiver may include a transmitter 1333and/or a receiver 1335 to implement transmitter or receiverfunctionality, respectively, appropriate to the RAN links (e.g.,frequency allocations and the like). Further, the transmitter 1333 andthe receiver 1335 of each transceiver may share circuit components,software, or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of thecommunication subsystem 1331 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the Global Positioning System (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, the communication subsystem 1331 may includecellular communication, WiFi communication, Bluetooth communication, andGPS communication. The network 1343B may encompass wired and/or wirelessnetworks such as a LAN, a WAN, a computer network, a wireless network, atelecommunications network, another like network, or any combinationthereof. For example, the network 1343B may be a cellular network, aWiFi network, and/or a near-field network. A power source 1313 may beconfigured to provide Alternating Current (AC) or Direct Current (DC)power to components of the UE 1300.

The features, benefits, and/or functions described herein may beimplemented in one of the components of the UE 1300 or partitionedacross multiple components of the UE 1300. Further, the features,benefits, and/or functions described herein may be implemented in anycombination of hardware, software, or firmware. In one example, thecommunication subsystem 1331 may be configured to include any of thecomponents described herein. Further, the processing circuitry 1301 maybe configured to communicate with any of such components over the bus1302. In another example, any of such components may be represented byprogram instructions stored in memory that, when executed by theprocessing circuitry 1301, perform the corresponding functions describedherein. In another example, the functionality of any of such componentsmay be partitioned between the processing circuitry 1301 and thecommunication subsystem 1331. In another example, thenon-computationally intensive functions of any of such components may beimplemented in software or firmware and the computationally intensivefunctions may be implemented in hardware.

FIG. 14 is a schematic block diagram illustrating a virtualizationenvironment 1400 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices, and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a WD, or any other type of communicationdevice) or components thereof and relates to an implementation in whichat least a portion of the functionality is implemented as one or morevirtual components (e.g., via one or more applications, components,functions, virtual machines, or containers executing on one or morephysical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 1400 hosted byone or more of hardware nodes 1430. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 1420 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. The applications 1420 arerun in the virtualization environment 1400 which provides hardware 1430comprising processing circuitry 1460 and memory 1490. The memory 1490contains instructions 1495 executable by the processing circuitry 1460whereby the application 1420 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

The virtualization environment 1400 comprises general-purpose orspecial-purpose network hardware devices 1430 comprising a set of one ormore processors or processing circuitry 1460, which may be CommercialOff-the-Shelf (COTS) processors, dedicated ASICs, or any other type ofprocessing circuitry including digital or analog hardware components orspecial purpose processors. Each hardware device 1430 may comprisememory 1490-1 which may be non-persistent memory for temporarily storinginstructions 1495 or software executed by the processing circuitry 1460.Each hardware device 1430 may comprise one or more Network InterfaceControllers (NICs) 1470, also known as network interface cards, whichinclude a physical network interface 1480. Each hardware device 1430 mayalso include non-transitory, persistent, machine-readable storage media1490-2 having stored therein software 1495 and/or instructionsexecutable by the processing circuitry 1460. The software 1495 mayinclude any type of software including software for instantiating one ormore virtualization layers 1450 (also referred to as hypervisors),software to execute virtual machines 1440, as well as software allowingit to execute functions, features, and/or benefits described in relationwith some embodiments described herein.

The virtual machines 1440, comprise virtual processing, virtual memory,virtual networking or interface, and virtual storage, and may be run bya corresponding virtualization layer 1450 or hypervisor. Differentembodiments of the instance of virtual appliance 1420 may be implementedon one or more of the virtual machines 1440, and the implementations maybe made in different ways.

During operation, the processing circuitry 1460 executes the software1495 to instantiate the hypervisor or virtualization layer 1450, whichmay sometimes be referred to as a Virtual Machine Monitor (VMM). Thevirtualization layer 1450 may present a virtual operating platform thatappears like networking hardware to the virtual machine 1440.

As shown in FIG. 14, the hardware 1430 may be a standalone network nodewith generic or specific components. The hardware 1430 may comprise anantenna 14225 and may implement some functions via virtualization.Alternatively, the hardware 1430 may be part of a larger cluster ofhardware (e.g., such as in a data center or CPE) where many hardwarenodes work together and are managed via a Management and Orchestration(MANO) 14100, which, among others, oversees lifecycle management of theapplications 1420.

Virtualization of the hardware is in some contexts referred to asNetwork Function Virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers and CPE.

In the context of NFV, the virtual machine 1440 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of the virtualmachines 1440, and that part of the hardware 1430 that executes thatvirtual machine 1440, be it hardware dedicated to that virtual machine1440 and/or hardware shared by that virtual machine 1440 with others ofthe virtual machines 1440, forms a separate Virtual Network Element(VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 1440 on top of the hardware networkinginfrastructure 1430 and corresponds to the application 1420 in FIG. 14.

In some embodiments, one or more radio units 14200 that each include oneor more transmitters 14220 and one or more receivers 14210 may becoupled to the one or more antennas 14225. The radio units 14200 maycommunicate directly with the hardware nodes 1430 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of acontrol system 14230, which may alternatively be used for communicationbetween the hardware nodes 1430 and the radio unit 14200.

FIG. 15 illustrates a communication system according to some embodimentsof the present disclosure. With reference to FIG. 15, in accordance withan embodiment, a communication system includes a telecommunicationnetwork 1510, such as a 3GPP-type cellular network, which comprises anaccess network 1511, such as a RAN, and a core network 1514. The accessnetwork 1511 comprises a plurality of base stations 1512A, 1512B, 1512C,such as NBs, eNBs, gNBs, or other types of wireless APs, each defining acorresponding coverage area 1513A, 1513B, 1513C. Each base station1512A, 1512B, 1512C is connectable to the core network 1514 over a wiredor wireless connection 1515. A first UE 1591 located in coverage area1513C is configured to wirelessly connect to, or be paged by, thecorresponding base station 1512C. A second UE 1592 in coverage area1513A is wirelessly connectable to the corresponding base station 1512A.While a plurality of UEs 1591, 1592 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 1512.

The telecommunication network 1510 is itself connected to a hostcomputer 1530, which may be embodied in the hardware and/or software ofa standalone server, a cloud-implemented server, a distributed server,or as processing resources in a server farm. The host computer 1530 maybe under the ownership or control of a service provider, or may beoperated by the service provider or on behalf of the service provider.Connections 1521 and 1522 between telecommunication network 1510 and thehost computer 1530 may extend directly from the core network 1514 to thehost computer 1530 or may go via an optional intermediate network 1520.The intermediate network 1520 may be one of, or a combination of morethan one of, a public, private, or hosted network; the intermediatenetwork 1520, if any, may be a backbone network or the Internet; inparticular, the intermediate network 1520 may comprise two or moresub-networks (not shown).

The communication system of FIG. 15 as a whole enables connectivitybetween the connected UEs 1591, 1592 and the host computer 1530. Theconnectivity may be described as an Over-the-Top (OTT) connection 1550.The host computer 1530 and the connected UEs 1591, 1592 are configuredto communicate data and/or signaling via the OTT connection 1550, usingthe access network 1511, the core network 1514, any intermediate network1520, and possible further infrastructure (not shown) as intermediaries.The OTT connection 1550 may be transparent in the sense that theparticipating communication devices through which the OTT connection1550 passes are unaware of routing of uplink and downlinkcommunications. For example, the base station 1512 may not or need notbe informed about the past routing of an incoming downlink communicationwith data originating from the host computer 1530 to be forwarded (e.g.,handed over) to a connected UE 1591. Similarly, the base station 1512need not be aware of the future routing of an outgoing uplinkcommunication originating from the UE 1591 towards the host computer1530.

FIG. 16 illustrates a communication system according to some embodimentsof the present disclosure. Example implementations, in accordance withan embodiment, of the UE, base station, and host computer discussed inthe preceding paragraphs will now be described with reference to FIG.16. In a communication system 1600, a host computer 1610 compriseshardware 1615 including a communication interface 1616 configured to setup and maintain a wired or wireless connection with an interface of adifferent communication device of the communication system 1600. Thehost computer 1610 further comprises processing circuitry 1618, whichmay have storage and/or processing capabilities. In particular, theprocessing circuitry 1618 may comprise one or more programmableprocessors, ASICs, FPGAs, or combinations of these (not shown) adaptedto execute instructions. The host computer 1610 further comprisessoftware 1611, which is stored in or accessible by the host computer1610 and executable by the processing circuitry 1618. The software 1611includes a host application 1612. The host application 1612 may beoperable to provide a service to a remote user, such as a UE 1630connecting via an OTT connection 1650 terminating at the UE 1630 and thehost computer 1610. In providing the service to the remote user, thehost application 1612 may provide user data which is transmitted usingthe OTT connection 1650.

The communication system 1600 further includes a base station 1620provided in a telecommunication system and comprising hardware 1625enabling it to communicate with the host computer 1610 and with the UE1630. The hardware 1625 may include a communication interface 1626 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 1600, as well as a radio interface 1627 for setting up andmaintaining at least a wireless connection 1670 with the UE 1630 locatedin a coverage area (not shown in FIG. 16) served by the base station1620. The communication interface 1626 may be configured to facilitate aconnection 1660 to the host computer 1610. The connection 1660 may bedirect or it may pass through a core network (not shown in FIG. 16) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 1625 of the base station 1620 further includes processingcircuitry 1628, which may comprise one or more programmable processors,ASICs, FPGAs, or combinations of these (not shown) adapted to executeinstructions. The base station 1620 further has software 1621 storedinternally or accessible via an external connection.

The communication system 1600 further includes the UE 1630 alreadyreferred to. The UE's 1630 hardware 1635 may include a radio interface1637 configured to set up and maintain a wireless connection 1670 with abase station serving a coverage area in which the UE 1630 is currentlylocated. The hardware 1635 of the UE 1630 further includes processingcircuitry 1638, which may comprise one or more programmable processors,ASICs, FPGAs, or combinations of these (not shown) adapted to executeinstructions. The UE 1630 further comprises software 1631, which isstored in or accessible by the UE 1630 and executable by the processingcircuitry 1638. The software 1631 includes a client application 1632.The client application 1632 may be operable to provide a service to ahuman or non-human user via the UE 1630, with the support of the hostcomputer 1610. In the host computer 1610, the executing host application1612 may communicate with the executing client application 1632 via theOTT connection 1650 terminating at the UE 1630 and the host computer1610. In providing the service to the user, the client application 1632may receive request data from the host application 1612 and provide userdata in response to the request data. The OTT connection 1650 maytransfer both the request data and the user data. The client application1632 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 1610, the base station 1620, and theUE 1630 illustrated in FIG. 16 may be similar or identical to the hostcomputer 1530, one of the base stations 1512A, 1512B, 1512C, and one ofthe UEs 1591, 1592 of FIG. 15, respectively. This is to say, the innerworkings of these entities may be as shown in FIG. 16 and independently,the surrounding network topology may be that of FIG. 15.

In FIG. 16, the OTT connection 1650 has been drawn abstractly toillustrate the communication between the host computer 1610 and the UE1630 via the base station 1620 without explicit reference to anyintermediary devices and the precise routing of messages via thesedevices. The network infrastructure may determine the routing, which maybe configured to hide from the UE 1630 or from the service provideroperating the host computer 1610, or both. While the OTT connection 1650is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 1670 between the UE 1630 and the base station1620 is in accordance with the teachings of the embodiments describedthroughout this disclosure. One or more of the various embodimentsimprove the performance of OTT services provided to the UE 1630 usingthe OTT connection 1650, in which the wireless connection 1670 forms thelast segment. More precisely, the teachings of these embodiments mayimprove the flexibility of PDSCH-to-HARQ-timing compared to conventionalNR networks.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency, and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 1650 between the hostcomputer 1610 and the UE 1630, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring the OTT connection 1650 may beimplemented in the software 1611 and the hardware 1615 of the hostcomputer 1610 or in the software 1631 and the hardware 1635 of the UE1630, or both. In some embodiments, sensors (not shown) may be deployedin or in association with communication devices through which the OTTconnection 1650 passes; the sensors may participate in the measurementprocedure by supplying values of the monitored quantities exemplifiedabove, or supplying values of other physical quantities from which thesoftware 1611, 1631 may compute or estimate the monitored quantities.The reconfiguring of the OTT connection 1650 may include message format,retransmission settings, preferred routing, etc.; the reconfiguring neednot affect the base station 1620, and it may be unknown or imperceptibleto the base station 1620. Such procedures and functionalities may beknown and practiced in the art. In certain embodiments, measurements mayinvolve proprietary UE signaling facilitating the host computer 1610'smeasurements of throughput, propagation times, latency, and the like.The measurements may be implemented in that the software 1611 and 1631causes messages to be transmitted, in particular empty or ‘dummy’messages, using the OTT connection 1650 while it monitors propagationtimes, errors, etc.

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure. The communication system includes a host computer, a basestation, and a UE which may be those described with reference to FIGS.15 and 16. For simplicity of the present disclosure, only drawingreferences to FIG. 17 will be included in this section. In step 1710,the host computer provides user data. In sub-step 1711 (which may beoptional) of step 1710, the host computer provides the user data byexecuting a host application. In step 1720, the host computer initiatesa transmission carrying the user data to the UE. In step 1730 (which maybe optional), the base station transmits to the UE the user data whichwas carried in the transmission that the host computer initiated, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In step 1740 (which may also be optional), the UEexecutes a client application associated with the host applicationexecuted by the host computer.

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure. The communication system includes a host computer, a basestation, and a UE which may be those described with reference to FIGS.15 and 16. For simplicity of the present disclosure, only drawingreferences to FIG. 18 will be included in this section. In step 1810 ofthe method, the host computer provides user data. In an optionalsub-step (not shown) the host computer provides the user data byexecuting a host application. In step 1820, the host computer initiatesa transmission carrying the user data to the UE. The transmission maypass via the base station, in accordance with the teachings of theembodiments described throughout this disclosure. In step 1830 (whichmay be optional), the UE receives the user data carried in thetransmission.

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure. The communication system includes a host computer, a basestation, and a UE which may be those described with reference to FIGS.15 and 16. For simplicity of the present disclosure, only drawingreferences to FIG. 19 will be included in this section. In step 1910(which may be optional), the UE receives input data provided by the hostcomputer. Additionally or alternatively, in step 1920, the UE providesuser data. In sub-step 1921 (which may be optional) of step 1920, the UEprovides the user data by executing a client application. In sub-step1911 (which may be optional) of step 1910, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application may further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in sub-step 1930 (which may beoptional), transmission of the user data to the host computer. In step1940 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with some embodiments of the presentdisclosure. The communication system includes a host computer, a basestation, and a UE which may be those described with reference to FIGS.15 and 16. For simplicity of the present disclosure, only drawingreferences to FIG. 20 will be included in this section. In step 2010(which may be optional), in accordance with the teachings of theembodiments described throughout this disclosure, the base stationreceives user data from the UE. In step 2020 (which may be optional),the base station initiates transmission of the received user data to thehost computer. In step 2030 (which may be optional), the host computerreceives the user data carried in the transmission initiated by the basestation.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include DSPs, special-purpose digital logic, and thelike. The processing circuitry may be configured to execute program codestored in memory, which may include one or several types of memory suchas ROM, RAM, cache memory, flash memory devices, optical storagedevices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

The term unit may have conventional meaning in the field of electronics,electrical devices, and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Example Embodiments Group A Embodiments—Wireless Device Methods

1. A method, performed by a wireless device, for setting HARQ timing forPDSCH with a pending PDSCH-to-HARQ-timing-indicator, the methodcomprising: receiving first DCI associated with a first DL datatransmission, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator; receiving the first DL datatransmission; determining a HARQ feedback for the first DL datatransmission; receiving second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location for HARQ feedbackassociated with the second DL data transmission; setting the location ofHARQ feedback associated with the first DL data transmission to be thesame as the location of HARQ feedback associated with the second DL datatransmission; and transmitting the HARQ feedback associated with thefirst DL data transmission at the set location.

2. A method, performed by a wireless device, for setting HARQ timing forPDSCH with a pending PDSCH-to-HARQ-timing-indicator, the methodcomprising: receiving first DCI associated with a first DL datatransmission of a first PDSCH group, the first DCI comprising anon-numerical PDSCH-to-HARQ-timing-indicator; receiving the first DLdata transmission; determining a HARQ feedback for the first DL datatransmission; receiving second DCI associated with a second DL datatransmission, the second DCI comprising a numericalPDSCH-to-HARQ-timing-indicator indicating a location for HARQ feedbackassociated with the second DL data transmission; determining that thesecond DL data transmission is of the same PDSCH group as the first DLdata transmission; setting the location of HARQ feedback associated withthe first DL data transmission to be the same as the location of HARQfeedback associated with the second DL data transmission; andtransmitting the HARQ feedback associated with the first DL datatransmission at the set location.

3. A method, performed by a wireless device, for setting HARQ timing forPDSCH with a pending PDSCH-to-HARQ-timing-indicator, the methodcomprising: receiving a first DCI associated with a first DL datatransmission of a first PDSCH group, the first DCI comprising anumerical PDSCH-to-HARQ-timing-indicator; determining that the locationfor the HARQ that is associated with the first DL data transmission,indicated by the numerical PDSCH-to-HARQ-timing-indicator, is too closeto the first dl data transmission; and in response to thatdetermination, not transmitting the HARQ that is associated with thefirst DL data transmission at the indicated HARQ transmission time.

4. The method of embodiment 3, further comprising providing anindication, on the PUCCH at the indicated HARQ transmission time, whichinforms the gNB that the HARQ feedback was postponed.

Group B Embodiments—gNB Methods

5. A method, performed by a gNB, for setting HARQ timing for PDSCH witha pending PDSCH-to-HARQ-timing-indicator, the method comprising:transmitting, to a first UE, a first DCI associated with a first DL datatransmission, the first DCI comprising a non-numericalPDSCH-to-HARQ-timing-indicator; transmitting, to the first UE, a secondDCI associated with a second DL data transmission, the second DCIcomprising a numerical PDSCH-to-HARQ-timing-indicator and at least oneof the following: at least one HARQ process ID; a NDI value; at leastone PDSCH group ID; a corresponding DAI; and/or a trigger bit.

Group C Embodiments—Apparatus

6. A wireless device for setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator, the wireless device comprising:processing circuitry configured to perform any of the steps of any ofthe Group A embodiments; and power supply circuitry configured to supplypower to the wireless device.

7. A base station for setting HARQ timing for PDSCH with a pendingPDSCH-to-HARQ-timing-indicator, the base station comprising: processingcircuitry configured to perform any of the steps of any of the Group Bembodiments; power supply circuitry configured to supply power to thebase station.

8. A User Equipment, UE, for setting HARQ timing for PDSCH with apending PDSCH-to-HARQ-timing-indicator, the UE comprising: an antennaconfigured to send and receive wireless signals; radio front-endcircuitry connected to the antenna and to processing circuitry, andconfigured to condition signals communicated between the antenna and theprocessing circuitry; the processing circuitry being configured toperform any of the steps of any of the Group A embodiments; an inputinterface connected to the processing circuitry and configured to allowinput of information into the UE to be processed by the processingcircuitry; an output interface connected to the processing circuitry andconfigured to output information from the UE that has been processed bythe processing circuitry; and a battery connected to the processingcircuitry and configured to supply power to the UE.

Group D Embodiments—System (with Host Computer)

9. A communication system including a host computer comprising:processing circuitry configured to provide user data; and acommunication interface configured to forward the user data to acellular network for transmission to a User Equipment, UE, wherein thecellular network comprises a base station having a radio interface andprocessing circuitry, the base station's processing circuitry configuredto perform any of the steps of any of the Group B embodiments.

10. The communication system of the previous embodiment furtherincluding the base station.

11. The communication system of the previous 2 embodiments, furtherincluding the UE, wherein the UE is configured to communicate with thebase station.

12. The communication system of the previous 3 embodiments, wherein: theprocessing circuitry of the host computer is configured to execute ahost application, thereby providing the user data; and the UE comprisesprocessing circuitry configured to execute a client applicationassociated with the host application.

13. A method implemented in a communication system including a hostcomputer, a base station and a User Equipment, UE, the methodcomprising: at the host computer, providing user data; and at the hostcomputer, initiating a transmission carrying the user data to the UE viaa cellular network comprising the base station, wherein the base stationperforms any of the steps of any of the Group B embodiments.

14. The method of the previous embodiment, further comprising, at thebase station, transmitting the user data.

15. The method of the previous 2 embodiments, wherein the user data isprovided at the host computer by executing a host application, themethod further comprising, at the UE, executing a client applicationassociated with the host application.

16. A User Equipment, UE, configured to communicate with a base station,the UE comprising a radio interface and processing circuitry configuredto perform the method of the previous 3 embodiments.

17. A communication system including a host computer comprising:processing circuitry configured to provide user data; and acommunication interface configured to forward user data to a cellularnetwork for transmission to a User Equipment, UE, wherein the UEcomprises a radio interface and processing circuitry, the UE'scomponents configured to perform any of the steps of any of the Group Aembodiments.

18. The communication system of the previous embodiment, wherein thecellular network further includes a base station configured tocommunicate with the UE.

19. The communication system of the previous 2 embodiments, wherein: theprocessing circuitry of the host computer is configured to execute ahost application, thereby providing the user data; and the UE'sprocessing circuitry is configured to execute a client applicationassociated with the host application.

20. A method implemented in a communication system including a hostcomputer, a base station and a User Equipment, UE, the methodcomprising: at the host computer, providing user data; and at the hostcomputer, initiating a transmission carrying the user data to the UE viaa cellular network comprising the base station, wherein the UE performsany of the steps of any of the Group A embodiments.

21. The method of the previous embodiment, further comprising at the UE,receiving the user data from the base station.

22. A communication system including a host computer comprising:communication interface configured to receive user data originating froma transmission from a User Equipment, UE, to a base station, wherein theUE comprises a radio interface and processing circuitry, the UE'sprocessing circuitry configured to perform any of the steps of any ofthe Group A embodiments.

23. The communication system of the previous embodiment, furtherincluding the UE.

24. The communication system of the previous 2 embodiments, furtherincluding the base station, wherein the base station comprises a radiointerface configured to communicate with the UE and a communicationinterface configured to forward to the host computer the user datacarried by a transmission from the UE to the base station.

25. The communication system of the previous 3 embodiments, wherein: theprocessing circuitry of the host computer is configured to execute ahost application; and the UE's processing circuitry is configured toexecute a client application associated with the host application,thereby providing the user data.

26. The communication system of the previous 4 embodiments, wherein: theprocessing circuitry of the host computer is configured to execute ahost application, thereby providing request data; and the UE'sprocessing circuitry is configured to execute a client applicationassociated with the host application, thereby providing the user data inresponse to the request data.

27. A method implemented in a communication system including a hostcomputer, a base station and a User Equipment, UE, the methodcomprising: at the host computer, receiving user data transmitted to thebase station from the UE, wherein the UE performs any of the steps ofany of the Group A embodiments.

28. The method of the previous embodiment, further comprising, at theUE, providing the user data to the base station.

29. The method of the previous 2 embodiments, further comprising: at theUE, executing a client application, thereby providing the user data tobe transmitted; and at the host computer, executing a host applicationassociated with the client application.

30. The method of the previous 3 embodiments, further comprising: at theUE, executing a client application; and at the UE, receiving input datato the client application, the input data being provided at the hostcomputer by executing a host application associated with the clientapplication, wherein the user data to be transmitted is provided by theclient application in response to the input data.

31. A communication system including a host computer comprising acommunication interface configured to receive user data originating froma transmission from a User Equipment, UE, to a base station, wherein thebase station comprises a radio interface and processing circuitry, thebase station's processing circuitry configured to perform any of thesteps of any of the Group B embodiments.

32. The communication system of the previous embodiment furtherincluding the base station.

33. The communication system of the previous 2 embodiments, furtherincluding the UE, wherein the UE is configured to communicate with thebase station.

34. The communication system of the previous 3 embodiments, wherein: theprocessing circuitry of the host computer is configured to execute ahost application; the UE is configured to execute a client applicationassociated with the host application, thereby providing the user data tobe received by the host computer.

35. A method implemented in a communication system including a hostcomputer, a base station and a User Equipment, UE, the methodcomprising: at the host computer, receiving, from the base station, userdata originating from a transmission which the base station has receivedfrom the UE, wherein the UE performs any of the steps of any of theGroup A embodiments.

36. The method of the previous embodiment, further comprising at thebase station, receiving the user data from the UE.

37. The method of the previous 2 embodiments, further comprising at thebase station, initiating a transmission of the received user data to thehost computer. According to some aspects of the present disclosure, amethod, performed by a wireless device, for setting HARQ timing forPDSCH with a pending PDSCH-to-HARQ-timing-indicator, comprises:receiving a first DCI associated with a first DL data transmission, thefirst DCI comprising a non-numerical PDSCH-to-HARQ-timing-indicator;receiving the first DL data transmission; determining a HARQ feedbackfor the first DL data transmission; receiving a second DCI associatedwith a second DL data transmission, the second DCI comprising anumerical PDSCH-to-HARQ-timing-indicator indicating a location for HARQfeedback associated with the second DL data transmission; setting thelocation of HARQ feedback associated with the first DL data transmissionto be the same as the location of HARQ feedback associated with thesecond DL data transmission; and transmitting the HARQ feedbackassociated with the first DL data transmission at the set location.

Abbreviations

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   2G Second Generation    -   3G Third Generation    -   3GPP Third Generation Partnership Project    -   4G Fourth Generation    -   5G Fifth Generation    -   AC Alternating Current    -   ACK Acknowledge    -   AF Application Function    -   AMF Core Access and Mobility Management Function    -   AN Access Network    -   AP Access Point    -   ASIC Application Specific Integrated Circuit    -   ATM Asynchronous Transfer Mode    -   AUSF Authentication Server Function    -   BS Base Station    -   BSC Base Station Controller    -   BTS Base Transceiver Station    -   CA Carrier Aggregation    -   CBG Code Block Group    -   CD Compact Disk    -   CDMA Code Division Multiple Access    -   COT Channel Occupancy Time    -   COTS Commercial Off-The-Shelf    -   CPE Customer Premise Equipment    -   CPU Central Processing Unit    -   D2D Device-to-Device    -   DAI Downlink Assignment Indicator    -   DAS Distributed Antenna System    -   DC Direct Current    -   DCI Downlink Control Information    -   DIMM Dual In-Line Memory Module    -   DL Downlink    -   DN Data Network    -   DSP Digital Signal Processor    -   DVD Digital Video Disk    -   EEPROM Electrically Erasable Programmable Read Only Memory    -   eMTC Enhanced Machine-Type Communication    -   eNB Evolved Node B    -   EPROM Erasable Programmable Read Only Memory    -   E-SMLC Evolved Serving Mobile Location Center    -   FPGA Field Programmable Gate Array    -   GHz Gigahertz    -   gNB New Radio Base Station    -   GPS Global Positioning System    -   GSM Global System for Mobile Communications    -   HARQ Hybrid Automatic Repeat Request    -   HDDS Holographic Digital Data Storage    -   HD-DVD High-Density Digital Versatile Disc    -   I/O Input and Output    -   IoT Internet of Things    -   IP Internet Protocol    -   kHz kilohertz    -   L1 Layer 1    -   LAN Local Area Network    -   LBT Listen Before Talk    -   LEE Laptop Embedded Equipment    -   LME Laptop Mounted Equipment    -   LTE Long Term Evolution    -   M2M Machine-to-Machine    -   MANO Management and Orchestration    -   MCE Multi-Cell/Multicast Coordination Entity    -   MDT Minimization of Drive Tests    -   MIMO Multiple Input Multiple Output    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   MSR Multi-Standard Radio    -   MTC Machine-Type Communication    -   NACK Negative Acknowledge    -   NB-IoT Narrowband Internet of Things    -   NDI New Data Indicator    -   NEF Network Exposure Function    -   NFV Network Function Virtualization    -   NIC Network Interface Controller    -   NR New Radio    -   NRF Network Function Repository Function    -   NR-U New Radio in the Unlicensed spectrum    -   NSSF Network Slice Selection Function    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   OSS Operations Support System    -   OTT Over-the-Top    -   PCF Policy Control Function    -   PDA Personal Digital Assistant    -   PDCCH Physical Downlink Control Channel    -   PDSCH Physical Downlink Shared Channel    -   PROM Programmable Read Only Memory    -   PSTN Public Switched Telephone Networks    -   PUCCH Physical Uplink Control Channel    -   QoS Quality of Service    -   RAID Redundant Array of Independent Disks    -   RAM Random Access Memory    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RF Radio Frequency    -   RNC Radio Network Controller    -   ROM Read Only Memory    -   RRC Radio Resource Control    -   RRH Remote Radio Head    -   RRU Remote Radio Unit    -   RTT Round Trip Time    -   RUIM Removable User Identity    -   SDRAM Synchronous Dynamic Random Access Memory    -   SIM Subscriber Identity Module    -   SMF Session Management Function    -   SOC System on a Chip    -   SON Self-Organizing Network    -   SONET Synchronous Optical Networking    -   SPS Semi-Persistent Scheduling    -   TB Transport Block    -   TCP Transmission Control Protocol    -   TDD Time Division Duplexing    -   UCI Uplink Control Information    -   UDM Unified Data Management    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunications System    -   USB Universal Serial Bus    -   UTRAN Universal Terrestrial Radio Access Network    -   V2I Vehicle-to-Infrastructure    -   V2V Vehicle-to-Vehicle    -   V2X Vehicle-to-Everything    -   VMM Virtual Machine Monitor    -   VNE Virtual Network Element    -   VNF Virtual Network Function    -   VoIP Voice over Internet Protocol    -   WAN Wide Area Network    -   WCDMA Wideband Code Division Multiple Access    -   WD Wireless Device    -   WiMax Worldwide Interoperability for Microwave Access    -   WLAN Wireless Local Area Network

Those skilled in the art will recognize improvements and modificationsto the embodiments of the present disclosure. All such improvements andmodifications are considered within the scope of the concepts disclosedherein.

1. A method, performed by a wireless device, the method comprising:receiving a first Downlink Control Information, DCI, associated with afirst Downlink, DL, data transmission, the first DCI comprising aPhysical Downlink Shared Channel, PDSCH-to-Hybrid Automatic RepeatRequest, HARQ-timing-indicator having a first value indicating that HARQfeedback for the first DL data transmission is to occur once thewireless device has received a DCI comprising a numericalPDSCH-to-HARQ-timing-indicator having a value different from the firstvalue; receiving the first DL data transmission; receiving a second DCIassociated with a second DL data transmission, the second DCI comprisinga numerical PDSCH-to-HARQ-timing-indicator indicating a location in timefor HARQ feedback associated with the second DL data transmission;transmitting the HARQ feedback associated with the first DL datatransmission at the same location in time as that of HARQ feedbackassociated with the second DL data transmission.
 2. The method of claim1, wherein receiving the second DCI comprises receiving informationindicating a number of how many HARQ processes should be reported, thenumber including all pending PDSCHs and all PDSCHs having a DCIcomprising a PDSCH-to-HARQ-timing-indicator having the first value sincea last PDSCH has the DCI comprising the numericalPDSCH-to-HARQ-timing-indicator having the value different from the firstvalue.
 3. The method of claim 2, wherein receiving the informationindicating a number of how many HARQ processes should be reportedcomprises receiving a Downlink Assignment Indicator, DAI.
 4. The methodof claim 1, further comprising, subsequent to receiving the second DCIassociated with the second DL data transmission, determining that thesecond DL data transmission is indicated as being of a same PDSCH groupas the first DL data transmission, wherein transmitting the HARQfeedback associated with the first DL data transmission at the samelocation in time as that of the HARQ feedback associated with the secondDL data transmission is performed upon determining that the second DLdata transmission is indicated as being of a same PDSCH group as thefirst DL data transmission.
 5. The method of claim 1 wherein receivingthe second DCI associated with the second DL data transmission comprisesreceiving a User Equipment, UE, -specific DCI transmitted on a PhysicalDownlink Control Channel, PDCCH, the UE-specific DCI comprising thePDSCH-to-HARQ-timing-indicator.
 6. The method of claim 5 wherein theUE-specific DCI further comprises a HARQ process Identifier, ID.
 7. Themethod of claim 5 wherein the UE-specific DCI further comprises a NewData Indicator, NDI, value corresponding to the HARQ process ID.
 8. Themethod of claim 5 where the UE-specific DCI further comprises a PDSCHgroup ID and a corresponding Downlink Assignment Indicator, DAI.
 9. Themethod of claim 5 wherein the UE-specific DCI further comprises atrigger bit indicating that the PDSCH-to-HARQ-timing-indicator isapplicable to all PDSCHs with the PDSCH-to-HARQ-timing-indicator havingthe first value. 10-18. (canceled)
 19. The method of claim 1, whereinthe PDSCH-to-HARQ-timing-indicator having the first value is a numericalPDSCH-to-HARQ-timing-indicator indicating that the HARQ feedback for thefirst DL data transmission should be delayed until the wireless devicehas received the DCI comprising the numericalPDSCH-to-HARQ-timing-indicator having a value different from the firstvalue.
 20. The method of claim 19, wherein the first value comprises anexisting PDSCH-to-HARQ-timing-indicator value that has been remappedfrom indicating a delay value to indicating that HARQ transmissionsshould be delayed until the wireless device has received the DCIcomprising the numerical PDSCH-to-HARQ-timing-indicator having a valuedifferent from the first value.
 21. The method of claim 20 wherein,prior to receiving the first DCI, the wireless device receives aninstruction to remap the existing PDSCH-to-HARQ-timing-indicator valuefrom indicating the delay value to indicating that the HARQtransmissions should be delayed until the wireless device has receivedthe DCI comprising the numerical PDSCH-to-HARQ-timing-indicator having avalue different from the first value.
 22. The method of claim 19,wherein the first value comprises an additional bit that has been addedto an existing PDSCH-to-HARQ-timing-indicator value bit field in theDCI.
 23. A method, performed by a base station, the method comprising:determining a Physical Downlink Shared Channel, PDSCH-to-HybridAutomatic Repeat Request, HARQ-timing for an upcoming Downlink, DL, datatransmission to a User Equipment, UE; determining that HARQ feedback forthe upcoming DL data transmission should be delayed by the UE untilfurther notification from the base station; and transmitting, to the UE,a first Downlink Control Information, DCI, associated with the upcomingDL data transmission, the first DCI comprising a firstPDSCH-to-HARQ-timing-indicator value for indicating to the UE that theHARQ feedback for the upcoming DL data transmission should be delayeduntil further notification from the base station.
 24. The method ofclaim 23 wherein determining that the HARQ feedback for the upcoming DLdata transmission should be delayed by the UE until further notificationfrom the base station comprises determining that a processing delay fromthe end of the upcoming DL data transmission to the beginning of theHARQ feedback opportunity is less than a minimum threshold delay. 25.(canceled)
 26. The method of claim 23 wherein the firstPDSCH-to-HARQ-timing-indicator value comprises an existingPDSCH-to-HARQ-timing-indicator value that has been remapped fromindicating a delay value to indicating that HARQ transmissions should bedelayed until a wireless device has received a DCI comprising anumerical PDSCH-to-HARQ-timing-indicator having a value different fromthe first value.
 27. The method of claim 26 wherein, prior to sendingthe first DCI, the base station sends, to the UE, an instruction toremap the existing PDSCH-to-HARQ-timing-indicator value from indicatingthe delay value to indicating that the HARQ transmissions should bedelayed until the wireless device has received the DCI comprising thenumerical PDSCH-to-HARQ-timing-indicator having a value different fromthe first value.
 28. The method of claim 23, wherein the firstPDSCH-to-HARQ-timing-indicator value comprises an additional bit thathas been added to an existing PDSCH-to-HARQ-timing-indicator value bitfield in the DCI.
 29. The method of claim 23 further comprisingtransmitting the further notification to the UE.
 30. The method of claim29 wherein transmitting the further notification to the UE comprisestransmitting a second DCI associated with a second DL data transmission,the second DCI comprising a numerical PDSCH-to-HARQ-timing-indicator.31. The method of claim 29 wherein transmitting the second DCI furthercomprises transmitting at least one of the following: a HARQ processIdentifier, ID; a New Data Indicator, NDI, value; a PDSCH group ID; aDownlink Assignment Indicator, DAI; or a trigger bit.
 32. A wirelessdevice comprising processing circuitry configured to: receive a firstDownlink Control Information, DCI, associated with a first Downlink, DL,data transmission, the first DCI comprising a Physical Downlink SharedChannel, PDSCH-to-Hybrid Automatic Repeat Request, HARQ-timing-indicatorhaving a first value indicating that HARQ feedback for the first DL datatransmission is to occur once the wireless device has received a DCIcomprising a numerical PDSCH-to-HARQ-timing-indicator having a valuedifferent from the first value; receive the first DL data transmission;receive a second DCI associated with a second DL data transmission, thesecond DCI comprising a numerical PDSCH-to-HARQ-timing-indicatorindicating a location in time for HARQ feedback associated with thesecond DL data transmission; transmit a HARQ feedback associated withthe first DL data transmission at the same location in time as that ofHARQ feedback associated with the second DL data transmission. 33.(canceled)
 34. (canceled)
 35. A base station comprising processingcircuitry configured to: determine a Physical Downlink Shared Channel,PDSCH-to-Hybrid Automatic Repeat Request, HARQ-timing for an upcomingDownlink, DL, data transmission to a User Equipment, UE; determine thatHARQ feedback for the upcoming DL data transmission should be delayed bythe UE until further notification from the base station; and transmit,to the UE, a first Downlink Control Information, DCI, associated with afirst DL data transmission, the first DCI comprising a firstPDSCH-to-HARQ-timing-indicator value for indicating to the UE that HARQfeedback for the first DL data transmission should be delayed untilfurther notification from the base station.
 36. (canceled) 37.(canceled)